Somewhere in every early career, being the reliable one turns into a trap. You catch the errors, you rewrite the deck at 11pm, and people start routing things through you because you always deliver. Then you look at your week and realize nothing moves unless you touch it. The habit that got you noticed has quietly become the ceiling you are stuck under, and the reason has nothing to do with how well you explain a task.
The general who watched four raids at once and stayed silent
In October 2003, Stanley McChrystal took command of the Joint Special Operations Task Force in Iraq. His force was running roughly 18 raids a month. Every decision of consequence climbed the chain of command and waited for someone senior to bless it, which meant the enemy moved faster than the people hunting them.
He changed one variable: who was allowed to decide. Under what he named empowered execution, decision authority moved down to the people closest to the problem, and the leadership job flipped to feeding those people information, a reversal of the old flow where subordinates reported up and leaders issued commands. By the end of August 2006, the same task force was running 300 raids a month.
What I want to convey is what he did with the technology in front of him. Sitting in the operations center with four or five live raids on screens, he had a radio and could have directed any of them at any second. He stayed quiet, on the grounds that he was not on the ground and could not hear what those soldiers were hearing. He called the approach "eyes on, hands off", and in Team of Teams he described the shift as leading like a gardener, "enabling rather than directing."
Output went up seventeen fold when the most qualified person in the building stopped approving things.
Why the work they hand back always looks worse to you
When the task comes back, it will look wrong. Your judgment on that point is compromised, and there is research explaining why.
Michael Norton, Daniel Mochon, and Dan Ariely ran four experiments in which people assembled IKEA boxes, folded origami, and built Lego sets, then bid money on their own creations. Participants valued their amateur output at roughly what expert work was worth and assumed everyone else would agree. The researchers called it the IKEA effect.
Your brain applies that same markup to the tracker you built and the process you invented. So the version handed back is being graded against an inflated benchmark, and "they did it worse" is usually "they did it differently, and you built the ruler."
Trusting that ruler has a price. Gallup studied 143 Inc. 500 CEOs and found the ones with high delegator talent posted an average three-year growth rate of 1,751 percent, 112 percentage points above the CEOs who held on, and generated 33 percent more revenue. Roughly three in four of the business owners Gallup studied scored limited to low on that trait.
Pick your first handoff by failure cost, not by readiness
Waiting until you feel ready keeps the task on your desk permanently, because ready means fully documented, and you will never fully document work you can still do faster yourself. Sort by damage instead. Ask one question about any task: if this comes back wrong, how long does it take to fix? Within a day, it qualifies. Choose the thing where being bad at delegating is survivable, because that is what buys you the reps.
Say the rung out loud
Handoffs collapse when two people stand on different rungs of authority and neither names which one it is. Four rungs, and you say the number:
- Rung 1. Do it exactly this way, show me before it goes anywhere.
- Rung 2. Look into it, bring me a recommendation, I decide.
- Rung 3. Decide and act, tell me before it goes out.
- Rung 4. Decide and act, tell me after or not at all.
Start people at rung 2 for anything visible to a client and rung 3 for internal work. Move them up one rung after each clean delivery, and say the number when you move it: "You're at rung 3 on this now."
The three-line handoff, written, not spoken
Verbal instructions evaporate in about two days. Write three lines:
- Outcome. What "done" looks like, containing a number or a date. "The client report goes out by 3pm Thursday, same format as last month, with month-over-month numbers."
- Boundaries. What they change freely and what they cannot touch alone. "Rework the layout however you like. Never change which metrics appear without asking."
- Check-in. One booked date, not an open door. "Draft to me Wednesday noon. That is the only review."
Boundaries are the lines people skip, and they are the ones that prevent the awkward rescue later.
When the questions start, do not answer them
For the first week they will ask you things the three lines already cover. Answering trains them to ask again, and you become a search engine with a calendar. Try this instead: "Good question. What would you do if I were on a plane?" Then wait through the silence. They usually have the answer and are checking whether it is safe to use it.
When the answer genuinely is not in the handoff, give it, then add that line to the written version so it is answered permanently and not just today.
Your move before Wednesday
Open last week's calendar. Circle every block where your actual contribution was approving something someone else had already finished. Pick the one where a wrong call would have cost less than a day of rework, and send this message today:
"Taking myself out of the loop on [task]. You own it going forward. You're at rung 3, so decide and act, just tell me before it goes out. First one is Thursday. Do not wait for me to review it."
Then let the first one be bad, and fix the handoff instead of the work.
Until next time, future leader.
